Looks like it won't be as easy as just updating the version in package.json :-(

To save the digging, the failure on Travis is on this line:

The test failure is unrelated.

@Nibbler999 is right.

@rauchg: Can you please fix this asap. It is holding a lot of us back!!!!!! Also please bump the version number.

Rebased and passing now :-)

Since node-v4.0.0 was just released, this is now even more useful to land/release.

+1 This is blocking the world for a lot of people.

+1 This is blocking the world for a lot of people.

That's a lot of annoy. ws are failed too much.

So what about bringing socketio to the [email protected]?

Restating the obvious: Until this lands, engine.io and its dependents will be uninstallable under node v4.0.0 (latest stable node).

@rauchg @nkzawa can you please merge and release this update? That would be so ❤️

FWIW, in addition to breaking dependent packages, this is causing administrative overhead for the maintainers of your dependencies due to users filing false positive issues (e.g. websockets/bufferutil#15, websockets/utf-8-validate#13)

Yeah, looks like it was bumped now.

Don't see it on master - https://github.com/socketio/engine.io/blob/master/package.json#L29

Strange looks like 1.5.3...master it was only bumped in a tag

https://github.com/socketio/engine.io/blob/1.5.3-patch/package.json

???

socketio/engine.io-client#420

:(

The package in the npm registry has the correct package.json, so npm i works.

Thanks @rauchg!

@SpainTrain Which version are you used?

@SpainTrain Which version are you used?

$ npm cache clean
$ npm info engine.io version
1.5.3

$ npm info engine.io dependencies

{ base64id: '0.1.0',
  debug: '1.0.3',
  'engine.io-parser': '1.2.1',
  ws: '0.8.0' }

Tks sir!

Fixed 1a115d3